Fixed the issue by preserving the user's last submitted search in sessionStorage. Only search term is put in sessionStorage, not PokéAPI response. TanStack Query is still responsible for the server data, whilst sessionStorage handles the UI state needed.

Changes:

• Saves the submitted search query in sessionStorage.
• Restores the search field when returning to the application.
• Recreates the search results from the Pokémon data managed by TanStack Query.
• Preserves the existing empty-search and no-results messages.
• Avoids storing API data in sessionStorage.

This has been tested:

• Successfull run of npm run lint and npm run build
• Manual testing of search function
• Verified that search field and results remain after clicking onto a Pokémon and navigating back.
• Tested empty searches and searches with no results.